Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.80%. Comparing base (f8721eb) to head (901e5f1).
⚠️ Report is 5 commits behind head on master.
✅ All tests successful. No failed tests found.

@@           Coverage Diff           @@
##           master   #11538   +/-   ##
=======================================
  Coverage   98.80%   98.80%           
=======================================
  Files         127      127           
  Lines       43380    43380           
  Branches     2326     2326           
=======================================
  Hits        42860    42860           
  Misses        370      370           
  Partials      150      150           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

CodSpeed Performance Report

Merging #11538 will not alter performance

_{Comparing jonathimer:patch-1 (901e5f1) with master (3a9120d)¹}

Summary

✅ 59 untouched

I note that it seems to fail to find our license. Is this maybe because it doesn't include the full license text in the file?

Backport to 3.13: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 6ae7c55 on top of patchback/backports/3.13/6ae7c55c9577a2a7f964a2466d438bc5c7c6446b/pr-11538

Backporting merged PR #11538 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.13/6ae7c55c9577a2a7f964a2466d438bc5c7c6446b/pr-11538 upstream/3.13

4. Now, cherry-pick PR Add Linux Foundation Health Score badge to README #11538 contents into that branch:

   $ git cherry-pick -x 6ae7c55c9577a2a7f964a2466d438bc5c7c6446b

   If it'll yell at you with something like fatal: Commit 6ae7c55c9577a2a7f964a2466d438bc5c7c6446b is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 6ae7c55c9577a2a7f964a2466d438bc5c7c6446b

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Add Linux Foundation Health Score badge to README #11538 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.13/6ae7c55c9577a2a7f964a2466d438bc5c7c6446b/pr-11538

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.